Factor UnknownNamedObjectException into its own class#28931
Merged
dakrone merged 4 commits intoelastic:masterfrom Mar 8, 2018
Merged
Factor UnknownNamedObjectException into its own class#28931dakrone merged 4 commits intoelastic:masterfrom
dakrone merged 4 commits intoelastic:masterfrom
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This moves the inner class
UnknownNamedObjectExceptionfromNamedXContentRegistryinto a top-level class. This is so thatNamedXContentRegistrydoesn't have to depend on StreamInput and StreamOutput.Relates to #28504